Fermi: GCN 18065XRT: One uncatalogued X-ray source has been detected, it is below the RASS
limit and shows no definitive signs of fading. Therefore, at the present time we cannot confirm this as the afterglow.

BAT: Despite being near the Galactic Plane and Bulge, both the fast-decaying XRT light curve and Fermi/GBM observation (GCN Circ. 17511) suggests that this source is more likely to be a short GRB than a SGR. In addition, there are no other BAT detections of this source before or since this trigger.UVOT: no detection

BAT: From the BAT spectrum, this event does not appear to be a short hard burst. The quickly fading X-ray lightcurve, however (to be reported in a later circular), does appear consistent with a SHB, and does not appear to be similar to the lightcurves of SGRs or other Galactic sources.UVOT: no detection

A Swift TOO request was approved to locate the afterglow with XRT, with the observation ID 20375. Unfortunately, the star tracker did not find enough targets to lock. Swift will not reobserve the target.XRT: no detectionUVOT: no detection

BAT: The current analysis of the BAT data does not allow us to distinguish between the interpretations of this event as either a GRB or galactic transient.XRT: It is likely that BAT trigger 565651 was a somewhat unusual GRB rather than a Galactic or extragalactic transient, in spite of its proximity to the Galactic center.UVOT: no detection

Due to an observing constraint, Swift did not slew until T0+48.4 minutes.XRT: Swift performed a second epoch observation and the X-ray object reported by is no longer detected, therefore confirming that this object was the afterglowUVOT: no detection

Even though this is a weak detection and it is on the Galactic Plane (lon,lat= 74,-1), we determine that this is probably a GRB, but can not rule out some other type of astrophysical source. We will need the full data set to make the determination.UVOT: no detection

A Swift TOO to determine the position of the x-ray afterglow has been approved, and will take place once the source comes out of constraint on February 19th.XRT: No bright X-ray afterglow is detected inside the refined BAT error circle.

Due to a Moon observing constraint, Swift could not slew to the BAT position until 13:16 UT on 2013 February 20.XRT: No X-ray afterglow is detected inside the refined BAT error circle.UVOT: no detection

This event has all appearances of a GRB: hard BAT spectrum, bright XRT initial detection and fading. Still, we note that the galactic coordinates are l=12 deg, b=2.5 deg, consistent with a galactic origin. We believe it is a GRB, but can not rule out a new galactic transient.UVOT: no detection

While the BAT lightcurve and spectral results are consistant with a GRB origin for this trigger, given that the galactic coordinates are (lon,lat)=(0.6,10.3) deg, we cannot rule out a galactic source origin.XRT: The fact that the XRT source is fading suggests that Swift trigger 530581 is most likely a GRB.UVOT: no detection

There were no real-time notices for this event because it occurred during a TDRSS outage. There was no automated slew to this BAT trigger because of a Moon constraint.Further discussion: GCN 13389XRT: 2 possible candidatesUVOT: no detection

This source is 2 degrees from the Galactic plane. Although the BAT lightcurve and energy distribution is typical for a GRB, the possibility of this being a Galactic source will have to be assessed from further observations.UVOT: no detection

Due to a Sun observing constraint, Swift cannot slew to the BAT position until 14:29 UT on 2012 January 12. There will thus be no XRT or UVOT data for this trigger before this time.This burst is only two degrees off the Galactic plane and could be a Galactic transient.

Due to an observing constraint, Swift cannot slew to the BAT position. There will thus be no XRT or UVOT data for this trigger. This trigger will be in moon constraint until approximately 06:30 UT on the 19th of September.

Due to the proximity of the burst to the Sun, Swift cannot slew to the BAT position. The burst does not become observable by Swift until November 7th; there will thus be no XRT or UVOT data for this trigger.

BAT: The observed T90 value for GRB 100724A is inconclusive. The relatively large spectral lag value and soft spectrum points towards long soft burst. Our conclusion is that this burst is likely to be in the long burst category.

Due to an observing constraint, Swift cannot slew to the BAT position. There will thus be no XRT or UVOT data for this trigger. No observations with XRT or UVOT will be possible for approximately the next 26 days.

Found in ground analysis after the Suzaku WAM alerted the IPN.The BAT position is inside the error box of a triangulation performed using Konus-Wind, BAT, Suzaku-WAM, and INTEGRAL-SPI-ACS data. A Swift TOO observation has been requested and approved.XRT: no detectionUVOT: no detection

Fermi: GCN 9962Burst occurred during a preplanned Swift slew maneuver. A strong source was found in a mosaic of images from BAT event data, which is often collected during slews. Reported position is the BAT position, not the Fermi position.XRT: no detectionUVOT: no detection

This was probably the same event as Fermi-GBM trigger 274721737. A Swift TOO has been requested and approved. The narrow-field instruments will observe the location approximately 13 hours after the burst.